Universal Access To All Knowledge
Home Donate | Store | Blog | FAQ | Jobs | Volunteer Positions | Contact | Bios | Forums | Projects | Terms, Privacy, & Copyright
Search: Advanced Search
Anonymous User (login or join us)
Upload

Reply to this post | See parent post | Go Back
View Post [edit]

Poster: Administrator, Curator, or StaffJonathan Aizen Date: Mar 10, 2004 11:20pm
Forum: etree Subject: Re: Format of text file for best import

The text file is only used to get the track titles (for the file format screen - the other form is another story).
Disc 1
01. song
02. song
03. song

Disc 2
01. song
02. song
03. song

Is probably the most straight-forward approach. The files should be named

abbYYYY-MM-DDdXXtXX.fmt

To maximize ability to match songs to files.

Jon

Reply to this post
Reply [edit]

Poster: xtifr Date: Mar 12, 2004 9:55pm
Forum: etree Subject: Re: Format of text file for best import

Just a quick suggestion: if you skip leading whitespace when looking for numerics, you'd be able to parse (e.g.):

1. Some song
2. Another song
...
10. Yet one more song
...

I just had to go in and manually edit the metadata for one of my old uploads, which I wouldn't have had to do if the parser worked this way.

Reply to this post
Reply [edit]

Poster: Unstoppable Drew Date: Mar 10, 2004 11:32pm
Forum: etree Subject: Re: Format of text file for best import

Yea, I was more thinking of the venue/location/source/linneage fields.
I've tended to put as the first line of the file:

Band name - Venue - Location - Date

and all that winds up in the venue field during import.

Reply to this post
Reply [edit]

Poster: Administrator, Curator, or StaffJonathan Aizen Date: Mar 11, 2004 12:38am
Forum: etree Subject: Re: Format of text file for best import

Oh. I did the parser a long time ago, so I don't quite remember. But, I know that if there is a line near the top with a comma, that'll be used as the location field. I can take a closer look, but I don't recall trying to auto-parse the venue field.

Most of the information is grabbed from db.etree.org based on checksums.

Reply to this post
Reply [edit]

Poster: Unstoppable Drew Date: Mar 11, 2004 2:20am
Forum: etree Subject: Re: Format of text file for best import

Well I can pretty much guarantee that none of what I'm uploading will show up in the etree database, as it's all uncirculated material from my own library.

What's the parser written in ? That'd be a nice way to streamline metatdata entry if there was well known set of labels to use in your text file.

Reply to this post
Reply [edit]

Poster: Administrator, Curator, or StaffJonathan Aizen Date: Mar 11, 2004 2:44am
Forum: etree Subject: Re: Format of text file for best import

The parser is written in PHP using Perl regular expressions.

The regular expression for the location field is: /(.*\, {0,1}[A-Za-z]{1,}.*)/

For the source field it is: /source: *(.*)/i

For the lineage field it is: /lineage: *(.*)/i or /transfer: (.*)/i

For the taper it is: /taped by: *(.*)/i

For the transferer it is: /transfered by: *(.*)/i or /conversion *: *(.*)/i

I hope this helps

Jon

Reply to this post
Reply [edit]

Poster: Administrator, Curator, or Staffgreenone Date: Mar 11, 2004 4:54am
Forum: etree Subject: Re: Format of text file for best import

Jon - just looking at the parser info. This is great to know! I couldn't help but notice the "transfered" by - shouldn't it be "transferred", with two R's?

--Dave

Reply to this post
Reply [edit]

Poster: Unstoppable Drew Date: Mar 11, 2004 4:32am
Forum: etree Subject: Re: Format of text file for best import

Awesome. That was exactly what I was looking for. Thanks Jon!